Repository navigation
Conversation
Check that the action keeps the stage grouping and the defaults it had, and that the task model accepts that grouping.
…le name The module description is left untranslated on purpose: it is the whole README, with reST directives and image URLs.
Contributor
The module replaced the whole context of the My Tasks action. Any other module that writes the same context, like sale_project, clashed with it and the last one to load or update won: in a database with both, the grouping by stage was lost. Set default_group_by on the list and kanban views made for My Tasks instead, and leave the context of the action as Odoo defines it. This also keeps my_tasks in the context, so the own sub-tasks are shown and the Gantt shows the absences of the user.
Contributor
|
@roboadhoc r+ nobump rebase-ff |
Contributor
|
Merge method set to rebase and fast-forward. |
roboadhoc
pushed a commit
that referenced
this pull request
Oct 29, 2026
Part-of: #155 Signed-off-by: Juan Carreras <[email protected]>
roboadhoc
pushed a commit
that referenced
this pull request
Oct 29, 2026
Check that the action keeps the stage grouping and the defaults it had, and that the task model accepts that grouping. Part-of: #155 Signed-off-by: Juan Carreras <[email protected]>
roboadhoc
pushed a commit
that referenced
this pull request
Oct 29, 2026
…le name The module description is left untranslated on purpose: it is the whole README, with reST directives and image URLs. Part-of: #155 Signed-off-by: Juan Carreras <[email protected]>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Migración de
project_my_tasks_by_stagea 20.0.Tarea: https://www.adhoc.inc/odoo/project.task/76687
Qué cambió
20.0.1.0.0einstallable.project.action_view_my_task. Fija el agrupado por etapa del proyecto (default_group_by="stage_id") en las vistas lista y kanban propias de "Mis tareas", y deja el contexto como lo define Odoo.sale_projectescribe el mismo contexto, y en una base con los dos se queda con él el que se cargó o actualizó último. En adhoc y cedent, que tienen ambos, el agrupado no se veía.'my_tasks': 1, así que "Mis tareas" muestra las subtareas propias del mismo proyecto que su tarea padre y, con Enterprise, el Gantt marca las ausencias de quien lo mira. Se va'all_task': 0, que ya no lee nadie.es.pore-exportado contra 20.0 y nombre del módulo traducido. La descripción queda sin traducir, porque es el README completo.Para revisar
projectse actualiza. En un salto de versión no pasa, porque se actualizan todos los módulos.Cómo se probó
sale_projectinstalado en esa base, "Mis tareas" agrupa por etapa del proyecto en lista y kanban, muestra las subtareas propias y el Gantt marca la ausencia del usuario.pre-commit runen verde.